Self-healing and diagnostic screen

ABSTRACT

A method, system, and computer program product for determining a level of cleanliness of a multi-touch screen display, characterizing objects that make contact with the screen, and initiating a specific maintenance action on the screen, based on screen cleanliness and the object(s) characterization(s). A screen diagnostic and maintenance (SDM) utility initiates a number of procedures to determine the type of object(s) and a set of characteristics of object(s) that make contact with the touch screen. Based on the results of the procedures, the SDM utility characterizes/identifies the object(s). In addition, the SDM utility initiates maintenance screen check(s) based on information stored in maintenance configuration file(s). Based on the results of the maintenance check(s), configuration file(s) data and type and characterization of the object(s) that have made contact with the screen, the SDM utility determines the type of maintenance that is performed and the timing/schedule of the maintenance action(s).

CROSS-REFERENCE TO RELATED APPLICATION

The present application claims priority under 35 U.S.C. §120 as adivisional application to application Ser. No. 11/962,346, entitled“SELF-HEALING AND DIAGNOSTIC SCREEN,” filed on Dec. 21, 2007, which ishereby incorporated by reference in its entirety.

BACKGROUND

1. Technical Field

The present invention generally relates to data processing systems andin particular to touch screen displays in data processing systems.

2. Description of the Related Art

Touch screen displays have been increasing in popularity in recentyears. Touch screens provide users with a convenient and efficient wayto interact with a computer system. However, in order to maintain thelevel of convenience, efficiency, and even safety, maintaining thecleanliness of the touch screen is an important issue. There is someexisting technology that provides a solution for the maintenance of thetouch screen. A few solutions focus on maintaining the level ofcleanliness based on the number of times a human makes contact with thescreen. Other solutions utilize a measurement of the screen's opacitylevel to determine whether maintenance/cleaning is required. Inaddition, the maintenance action provided by some of the currentsolutions relies on the fixed action of a maintenance facility (i.e., aprotection mechanism) that is integrated into the touch screen device.The current solutions place no particular focus on: (a) the detection ofmultiple inputs or objects coming into contact with a touch screen; or(b) the discernment of the type of inputs or objects; or (c) the type ofmaintenance actions needed in the particular type of environment.

SUMMARY OF ILLUSTRATIVE EMBODIMENTS

Disclosed are a method, system, and computer program product fordetermining a level of cleanliness of a touch screen display,characterizing an object that makes contact with the screen, andinitiating a specific maintenance action on the screen of a computersystem, based on screen cleanliness and the object characterization. Ascreen diagnostic and maintenance (SDM) utility initiates a number ofprocedures to determine a set of characteristics of an object(s) thatmakes contact with the touch screen. Based on the results of theprocedures, the SDM utility is able to characterize/identify the object.In addition, the SDM utility initiates the maintenance screen check(s)based on information stored in a maintenance configuration file(s).Based on the results of the maintenance check(s), data from theconfiguration file(s), and characterization of the object(s) which havemade contact with the screen, the SDM utility determines the type ofmaintenance that is performed and the schedule of the maintenanceaction.

The above as well as additional objectives, features, and advantages ofthe present invention will become apparent in the following detailedwritten description.

BRIEF DESCRIPTION OF THE DRAWINGS

The invention itself, as well as a preferred mode of use, furtherobjects, and advantages thereof, will best be understood by reference tothe following detailed description of an illustrative embodiment whenread in conjunction with the accompanying drawings, wherein:

FIG. 1 is a block diagram representation of an electronic deviceconfigured with a multi-touch screen, according to one embodiment of theinvention;

FIG. 2A illustrates a multi-detection touch screen display withinteracting user(s), according to one embodiment of the invention;

FIG. 2B is a block diagram of a multi-detection touch screenillustrating various factors affecting the level of cleanliness of thescreen and an example list of steps provided to resolve a maintenanceissue, according to one embodiment of the invention and;

FIG. 3 is a flow chart illustrating the process of characterizing objectcontact with a touch screen and determining the appropriate maintenanceaction, according to one embodiment of the invention.

DETAILED DESCRIPTION OF AN ILLUSTRATIVE EMBODIMENT

The illustrative embodiments provide a method, system, and computerprogram product for determining a level of cleanliness of a touch screendisplay, characterizing an object that makes contact with the screen,and initiating a specific maintenance action on the screen of a computersystem, based on screen cleanliness and the object characterization. Ascreen diagnostic and maintenance (SDM) utility initiates a number ofprocedures to determine a set of characteristics of an object(s) thatmakes contact with the touch screen. Based on the results of theprocedures, the SDM utility is able to characterize/identify the object.In addition, the SDM utility initiates the maintenance screen check(s)based on information stored in a maintenance configuration file(s).Based on the results of the maintenance check(s), data from theconfiguration file(s) and characterization of the object(s) which havemade contact with the screen, the SDM utility determines the type ofmaintenance that is performed and the schedule of the maintenanceaction.

Implementation of the embodiments enables enhanced functionality formaintenance actions involving a touch screen display by: (1) allowingmultiple input resolution; (2) allowing discernment of the variousinput; (3) allowing for fine granularity of maintenance actions; and (4)scheduling the maintenance actions to allow for some level of autonomyfor the user. Additionally, the described maintenance actions (5) do notrequire that the detection and maintenance mechanisms be tightly coupledand integrated directly into the body of the device (as provided with akiosk, for example).

In the following detailed description of exemplary embodiments of theinvention, specific exemplary embodiments in which the invention may bepracticed are described in sufficient details to enable those skilled inthe art to practice the invention, and it is to be understood that otherembodiments may be utilized and that logical, architectural,programmatic, mechanical, electrical and other changes may be madewithout departing from the spirit or scope of the present invention. Thefollowing detailed description is, therefore, not to be taken in alimiting sense, and the scope of the present invention is defined onlyby the appended claims.

Within the descriptions of the figures, similar elements are providedsimilar names and reference numerals as those of the previous figure(s).Where a later figure utilizes the element in a different context or withdifferent functionality, the element is provided a different leadingnumeral representative of the figure number (e.g., 1xx for FIGS. 1 and2xx for FIG. 2). The specific numerals assigned to the elements areprovided solely to aid in the description and not meant to imply anylimitations (structural or functional) on the invention.

It is understood that the use of specific component, device and/orparameter names are for example only and not meant to imply anylimitations on the invention. The invention may thus be implemented withdifferent nomenclature/terminology utilized to describe thecomponents/devices/parameters herein, without limitation. Each termutilized herein is to be given its broadest interpretation given thecontext in which that terms is utilized.

With reference now to FIG. 1, there is depicted a block diagramrepresentation of an electronic device (which is illustrated as, but notlimited to data processing system) configured with a multi-detectionvisual display screen (touch screen). Electronic device 100 comprises atleast one processor or central processing unit (CPU) 101 connected tosystem memory 106 via system interconnect/bus 102. Also connected tosystem bus 102 is I/O controller 115, which provides connectivity andcontrol for input devices, of which pointing device (or mouse) 116 andkeyboard 117 are illustrated. I/O controller 115 is also connected totouch screen interface 112 which is connected to input/output touchscreen display 118. Additionally, a multimedia drive 119 (e.g., CDRW orDVD drive) and USB (universal serial bus) hub 121 are illustrated,coupled to I/O controller. Multimedia drive 119 and USB hub 121 mayoperate as both input and output (storage) mechanisms. Electronic device100 also comprises storage 107, within which data/instructions/code maybe stored. Electronic device 100 further comprises maintenance logic 113which provides a number of maintenance notifications, including one ormore or a combination of the following: (1) a visual highlightingnotification, which involves a visual change in the area (i.e., variousgrades of lighting or dimming); (2) a sound notification, such as anaudio alert; (3) a sensory notification, which may include a completeusage restriction of the screen area; (4) a temperaturenotification/alert, whereby the area heats up or cools down, forexample; and (5) a resolution resizing around the defective area. It isappreciated that the above list is not meant to imply any limitations onthe type of notification that may be executed/implemented.

Electronic device 100 is also illustrated with a network interfacedevice (NID) 125, with which electronic device 100 connects to one ormore servers 133 via access network 130, such as the Internet. In thedescribed embodiments, network 130 is a worldwide collection of networksand gateways that utilize the Transmission Control Protocol/InternetProtocol (TCP/IP) suite of protocols to communicate with one another. Ofcourse, network access may also be provided via a number of differenttypes of networks, such as an intranet, a local area network (LAN), avirtual private network (VPN), or other wide area network (WAN) otherthan the Internet, for example.

Notably, in addition to the above described hardware components ofelectronic device 100, various features of the invention are completedvia software (or firmware) code or logic stored within memory 106 orother storage (e.g., storage 107) and executed by CPU 101. Thus,illustrated within memory 106 are a number of software/firmwarecomponents, including operating system (OS) 108 (e.g., MicrosoftWindows®, a trademark of Microsoft Corp, GNU®/Linux®, registeredtrademarks of the Free Software Foundation and Linus Torvalds, or AIX®,a registered trademark of IBM), maintenance configuration (file) 109,maintenance records (file) 114, Object Recognition Facility 111, andscreen diagnostic and maintenance (SDM) utility 110. In actualimplementation, maintenance configuration (file) 109, maintenancerecords (file) 114, Object Recognition Facility 111, and SDM utility 110may be combined as a single application collectively providing thevarious functions of each individual software component when thecorresponding code is executed by the CPU 101. For simplicity, SDMutility 110 is illustrated and described as a stand alone or separatesoftware/firmware component, which provides specific functions, asdescribed below.

CPU 101 executes SDM utility 110 as well as OS 108, which supports theuser interface features of SDM utility 110. In the illustrativeembodiment, SDM utility 110 generates/provides several graphical userinterfaces (GUI) to enable user interaction with, or manipulation of,the functional features of the utility (110). Among the softwarecode/instructions provided by SDM utility 110, and which are specific tothe invention, are: (a) code for detecting an occurrence of an objectmaking contact with a touch screen display of a computer system; (b)code for characterizing/identifying the object that makes contact withthe screen; and (c) code for initiating a specific maintenance action onthe screen of the computer system. For simplicity of the description,the collective body of code that enables these various features isreferred to herein as SDM utility 110. According to the illustrativeembodiment, when CPU 101 executes SDM utility 110, electronic device 100initiates a series of functional processes that enable the abovefunctional features as well as additional features/functionality, whichare described below within the description of FIGS. 2-3.

Those of ordinary skill in the art will appreciate that the hardware andbasic configuration depicted in FIG. 1 may vary. For example, otherdevices/components may be used in addition to or in place of thehardware depicted. The depicted example is not meant to implyarchitectural limitations with respect to the present invention. Thedata processing system depicted in FIG. 1 may be, for example, an IBMeServer pSeries system, a product of International Business MachinesCorporation in Armonk, N.Y., running the Advanced Interactive Executive(AIX) operating system or LINUX operating system.

In electronic device 100, SDM utility 110 detects contact from an objectat touch screen display 118. SDM utility 110 characterizes the object todetermine whether a maintenance action is required. Object recognitiontechnology may be used to facilitate a characterization of the object.The characterization of the object is important since contact withcertain objects may make touch screen 118 unusable. The types of objectsmaking contact with the touch screen may take various forms which mayinclude the following non-exhaustive list: (1) finger(s); (2) hand(s);(3) paper; (4) mist from the breath of a human being; (5) liquid; and(6) food. Sometimes multiple occurrences of contact by a particularobject (e.g., a user's hands/fingers) with the touch screen are requiredto activate a maintenance action. However, a single occurrence ofcontact by another object (e.g., liquid) with the touch screen may beenough to activate a maintenance notification and/or action. Forexample, a drink/liquid spilling (see FIG. 2B) on touch screen 118 maycreate a greater level of urgency (i.e., may be assigned a higher levelof maintenance priority) than bread crumbs coming into contact withtouch screen 118. Furthermore, in this case, perhaps only one occurrenceof a contact of this nature may be required to initiate a maintenanceaction. Thus, SDM utility 110 characterizes and distinguishes varioustypes of object contact. SDM utility 110 refers to configurationrecord(s) 109 to determine the type of maintenance action required andthe schedule of the action. For example, in the case of an objectcharacterized as a “liquid spill”, the maintenance action may be to“clean the entire touch screen surface” and the schedule may be“immediately”.

In electronic device 100, the maintenance notification (and/ormaintenance action) may take various forms. As utilized herein the termnotification and action may refer to a same activity or differentactivity of the SDM utility 110. That is, a notification may beconsidered an action, and vice versa, while some actions are notnotifications. For simplicity, the term “maintenance action” is used torepresent both a notification and an action taken by the SDM utility110. In particular, the maintenance action may be a combination of anyof the following and may not be limited to: (1) a visual change in thearea (i.e., various grades of lighting or dimming); (2) an audio alert;(3) a complete usage restriction of the screen area; (4) a temperaturealert (i.e. the area heats up or cools down); and (5) a resolutionresizing around the defective area. Multiple usage of the screenincreases the likelihood for maintenance due to normal wear-and-tear andalso creates a risk factor for germs/infection. Upon detection that thearea of the screen is unclean as determined by a preset threshold levelof cleanliness, the computer cross-references the user's prioritysetting for a cleaning action. A cleaning action may not be scheduledbased on a number of factors which may include priority, time of day,etc.

SDM utility 110 may initiate maintenance action in the form of a screenprotection mechanism. This mechanism may be executed by the computerbased on certain configurable conditions. To avoid integration of thismechanism within the touch screen surface, SDM utility 110 may initiatecommunication with the protection mechanism via blue-tooth capability.Blue-tooth capability enables communication between the protectionmechanism device and the computer in order to provide location detailsof the affected area to the protection mechanism device. SDM utility 110may allow the protection mechanism to be applied to the full surfacearea. Alternatively, SDM utility 110 may indicate that alayered/sectional screen protection to specific areas is desired. Thescreen protection mechanism may include the following: (1) a transparentfilm to be applied to or removed from the surface; and (2) a wipermechanism that dispenses cleaning material across the surface.

SDM utility 110 may employ an interaction or idleness level as a cue forscheduling a maintenance action on the screen surface. Based on thelevel of interaction or idleness, a time of day, ambient light ormovement around the screen surface, a maintenance cycle may beinitiated/scheduled.

FIG. 2A illustrates a touch screen display with multiple interactingusers, according to one embodiment of the invention. Object-screensystem 200 comprises touch screen display 118 with interactinguser(s)/object(s) 201. In object-screen system 200, SDM utility 110 iscapable of characterizing/identifying the object as a finger/hand. SDMutility 110 may further characterize “surface” characteristics of theobject, such that a finger with grease is characterized differently fromone with sweat (e.g., a sweaty or moist hand/finger). SDM utility 110 isable to distinguish between various types of contact in order todetermine scheduling based on a configured priority and to select themost appropriate maintenance action. In one embodiment, for example, SDMutility 110 may employ Object Recognition Facility 111 to facilitate thecharacterization of object 201.

FIG. 2B is a block diagram of a multi-detection touch screenillustrating factors affecting the level of cleanliness of the screenand an example list of steps provided by SDM utility 110 to assist auser in resolving a screen maintenance issue, according to embodimentsof the invention. Screen example 210 comprises touch screen 118.Disposed on touch screen 118 is liquid spill 211. A low pixel resolutionarea 212 of visual display on touch screen 118 is also illustrated. Asprovided within screen example 210, low resolution area 212 illustratesa section of the touch screen where clarity has been reduced.Additionally, a list with cleaning steps illustrated as maintenance list213 is displayed on touch screen 218.

One application of low pixel resolution area 212 involves SDM utility110 triggering an adjustment to the brightness, contrast, or degradationof screen resolution (bits per pixel) in an affected screen area. Forexample, with continual usage of the screen, SDM utility 110 may allowthe area to continually change (degrade) in clarity. Thus, SDM utility110 provides a visual indication of the level of dirtiness of that areaof the screen 118, and responds by causing the area of the screen 118 topartially lose clarity. In extreme situations, SDM utility 118 may fullyrestrict visual display at a portion of the screen.

SDM utility 110 may alert the user to a possible problem (e.g.,defective pixels, opaque/unclean section of the screen) with the surfacescreen via a constant indicator on or around the area affected. Theconstant indicator may include: (1) a visual effect such as highlightingor a display of icons, or arrows, on the screen; (2) a touch sensorymechanism by which the affected area becomes warmer or cooler to thetouch; and (3) an audio sensory mechanism in which a sound becomeslouder when a user/object gets within a certain proximity of theaffected area.

SDM utility 110 may discover that pixels on the screen may be defective,after a maintenance action, for example. Consequently, SDM utility 110may initiate a maintenance cycle to determine whether the pixel isactually “stuck” versus “dead” and then initiate the appropriate fix. Asa maintenance action, SDM utility 110 may also provide temporary lowresolution (212) of visual display on touch screen 118.

FIG. 3 is a flow chart illustrating a method by which the aboveprocesses of the illustrative embodiments are completed. Although themethod illustrated in FIG. 3 may be described with reference tocomponents shown in FIGS. 1-2, it should be understood that this ismerely for convenience and alternative components and/or configurationsthereof can be employed when implementing the various methods. Keyportions of the methods may be completed by SDM utility 110 executingwithin electronic device 100 (FIG. 1) and controlling specificoperations of/on electronic device 100, and the methods are thusdescribed from the perspective of either/both SDM utility 110 and themulti-touch screen (118).

The process of FIG. 3 begins at initiator block 301 and proceeds toblock 302, at which SDM utility 110 initiates an active mode. SDMutility 110 continuously monitors screen activity and initiatesactivities based on an external trigger (e.g., human contact) orinternal triggers as a result of a pre-determined configuration.Furthermore, all user and computer system interaction via a touch screenproceeds without interruption by SDM utility 110.

At block 303, SDM utility 110 detects contact of an object(s) with thetouch screen. SDM utility 110 initiates procedures to characterize theobject, as shown at block 304. These procedures which reveal theproperties of the object may include a number of the following: (1) aweight measurement; (2) a temperature measurement; (3) a location of theobject; (4) an opacity level of the object; (5) further procedures(which may generate visual images/photographs of objects coming intocontact with the touch screen, for example) to obtain data as inputs toan object recognition facility; and (6) multiple applications of the(measurement) procedures at various intervals in order to record changesin the object's properties over time. At block 305, SDM utility 110identifies/characterizes the object based on the procedures to obtainthe object characteristics. SDM utility 110 may determine whether theobject is a liquid or a solid, for example, based on an identificationof a set of properties of the object. The identification of the physicalstate may require multiple executions of a number of the precedingprocedures. For example, a first measurement taken at one time intervaland a second measurement taken subsequently may reveal the dynamicnature of a liquid, the location of which may change/expand as theliquid spreads across the touch screen. In addition, SDM utility 110 maybe able to predict the manner in which the liquid spreads across thescreen based on a computed viscosity of the liquid (obtained via theprocedures/measurements).

At block 306, SDM utility 110 records, in a maintenance results file inthe computer system, the occurrence of the contact of thecharacterized/identified object with the touch screen. Thus, SDM utility110 is able to track a particular type of occurrence of object contactand provide a determination of the ability of the contact by the objectwith the touch screen to affect the level of screen cleanliness, basedon the object characterization.

In addition to the measurement/maintenance procedures initiated by anexternal trigger, at a preset time period(s), SDM utility 110 initiatesa number of maintenance screen checks, as shown at block 307. The timingof the maintenance checks are preset by configuration settings in astored maintenance configuration file. The maintenance screen checks maybe executed to determine a cleanliness level of the screen. A level ofcleanliness may be determined by a reading(s) obtained via opacitysensors. The results of the maintenance checks are also recorded in theresults file.

At block 308, SDM utility 110 performs an analysis to determine whethera maintenance action on the touch screen is required by utilizing anumber of the following: (1) object characterization; (2) maintenancecheck results; and (3) maintenance configuration file(s). The objectcharacterization and the maintenance check results may be stored in themaintenance results file(s). At decision block 309, SDM utility 110determines whether a maintenance action(s) is required, based on theanalysis results. If, at block 309, SDM utility 110 determines that amaintenance action(s) is required, the process moves to block 310, atwhich SDM utility 110 determines the specific type of maintenanceaction(s) required based on the configuration file(s) and/or maintenanceresults file. At block 311, SDM utility 110 enters a maintenance modeand initiates a specific maintenance action. In one embodiment, list 213may be displayed on the visual display touch screen to provide amaintenance staff/user with a list of steps for completing maintenanceaction(s).

The maintenance action may take various forms and may be a combinationof a number of other maintenance actions. These maintenance actions areoutlined in the description of the figures. Once the maintenance actionis completed, as shown at block 312, active mode resumes (i.e., thesystem returns to the normal state of operation), and the processreturns to block 302 for continuous monitoring.

In the flow charts above, one or more of the methods are embodied as acomputer program product in a computer readable medium or containingcomputer readable code such that a series of steps are performed whenthe computer readable code is executed on a computing device. In someimplementations, certain steps of the methods are combined, performedsimultaneously or in a different order, or perhaps omitted, withoutdeviating from the spirit and scope of the invention. Thus, while themethod steps are described and illustrated in a particular sequence, useof a specific sequence of steps is not meant to imply any limitations onthe invention. Changes may be made with regards to the sequence of stepswithout departing from the spirit or scope of the present invention. Useof a particular sequence is therefore, not to be taken in a limitingsense, and the scope of the present invention is defined only by theappended claims.

As will be further appreciated, the processes in embodiments of thepresent invention may be implemented using any combination of software,firmware, or hardware. As a preparatory step to practicing the inventionin software, the programming code (whether software or firmware) willtypically be stored in one or more machine readable storage mediums suchas fixed (hard) drives, diskettes, optical disks, magnetic tape,semiconductor memories such as ROMs, PROMs, etc., thereby making anarticle of manufacture (or computer program product) in accordance withthe invention. The article of manufacture containing the programmingcode is used by either executing the code directly from the storagedevice, by copying the code from the storage device into another storagedevice such as a hard disk, RAM, etc., or by transmitting the code forremote execution using transmission type media such as digital andanalog communication links. The methods of the invention may bepracticed by combining one or more machine-readable storage devicescontaining the code according to the present invention with appropriateprocessing hardware to execute the code contained therein. An apparatusfor practicing the invention could be one or more processing devices andstorage systems containing or having network access to program(s) codedin accordance with the invention.

Thus, it is important that while an illustrative embodiment of thepresent invention is described in the context of a fully functionalcomputer (server) system with installed (or executed) software, thoseskilled in the art will appreciate that the software aspects of anillustrative embodiment of the present invention are capable of beingdistributed as a computer program product in a variety of forms, andthat an illustrative embodiment of the present invention applies equallyregardless of the particular type of media used to actually carry outthe distribution. By way of example, a nonexclusive list of types ofmedia includes recordable type (tangible) media such as floppy disks,thumb drives, hard disk drives, CD ROMs, DVDs, and transmission typemedia such as digital and analog communication links.

While the invention has been described with reference to exemplaryembodiments, it will be understood by those skilled in the art thatvarious changes may be made and equivalents may be substituted forelements thereof without departing from the scope of the invention. Inaddition, many modifications may be made to adapt a particular system,device or component thereof to the teachings of the invention withoutdeparting from the essential scope thereof. Therefore, it is intendedthat the invention not be limited to the particular embodimentsdisclosed for carrying out this invention, but that the invention willinclude all embodiments falling within the scope of the appended claims.Moreover, the use of the terms first, second, etc. do not denote anyorder or importance, but rather the terms first, second, etc. are usedto distinguish one element from another.

What is claimed is:
 1. An electronic device comprising: a processor; amemory system coupled to the processor and which stores one or more of amaintenance configuration file, a maintenance records file, and anobject recognition facility that facilitates characterization ofobjects; a multiple detection touch screen; a screen maintenancefacility executing on the process and which provides a number ofmaintenance actions, including one or more of: (1) a visual highlightingnotification; (2) a sound notification; and (3) a sensory andtemperature notification; a screen diagnostic and maintenance (SDM)utility which when executed by the processor enables the electronicdevice to: detect an occurrence of a contact by the object with thetouch screen; automatically determine a set of characteristics of theobject following the occurrence of the contact with the touch screen;dynamically activate a set of maintenance actions to enhance a level ofcleanliness of the touch screen, wherein said activating furthercomprises triggering the set of maintenance actions as a result of oneor more of: (1) a characteristic of a detected object (2) a thresholdlevel attained following the occurrence of the contact, wherein saidthreshold is based on a number of factors contained within a maintenanceconfiguration file; (3) an elapsed time interval since a lastmaintenance action; (4) an identified level of screen cleanliness thatis determined by one or more procedures, including utilization ofopacity sensors; (5) a time of day; (6) a level of interaction between auser and the touch screen; and (7) a set of configuration data; applythe set of maintenance actions, including one or more of: (1) a visualchange in a particular screen location; (2) an audio alert; (3) a usagerestriction of the screen area (4) a temperature alert; (5) amodification of a pixel resolution around the particular area (6) aconstant indicator, wherein said constant indicator includes one or moreof and is not limited to the following: (a) a visual effect thatincludes a highlighting mechanism facilitated by a display of one ormore of icons and arrows on the screen at a location within a presetrange of distances to the affected area (b) a touch sensory mechanismthat includes one or more of a heating and cooling of an affected screenarea when touched by the object; and (c) an audio sensory mechanism thatincludes a sound that increases in sound level when an object ispositioned within a defined proximity of the affected area (7) anapplication of a transparent film to the screen surface; and (8) autilization of a wiper mechanism that dispenses cleaning material acrossthe screen surface; display a list of maintenance tasks to be completedby a user to execute a maintenance action; enable execution of themaintenance action via the displayed list, wherein a user is able tointeract with said list to indicate a completion of one or more tasks onthe list; providing a maintenance action via an external screenprotection device, wherein said screen protection device has ablue-tooth capability, which enables communication between theprotection device and the electronic device in order to provide anappropriate set of details of the affected area of the screen to theprotection device; and detect one or more defects in one or more displayscreen pixels; and in response to detecting a defect, trigger a set ofmaintenance actions based on the defect of the display screen pixels;wherein a discovery of said defect of the screen pixels is facilitatedby one or more maintenance actions which include a cleaning action ofthe touch screen, wherein said maintenance actions enable anidentification of a persistent problem with the screen display, which isnot attributable to the level of cleanliness of the screen; and whereinsaid defect of the screen pixels is confirmed by a set of resultsobtained by a test of the screen pixels.
 2. The device of claim 1,wherein the SDM utility further configures the device to: store datapertaining to the set of characteristics of the object; and perform anumber of maintenance checks at specific time intervals based on one ormore of: (1) a set of configuration data; and (2) a set of data storedin one or more files of maintenance records and results.
 3. The deviceof claim 1, wherein said utility configuring the device to determinefurther configures the device to: identify the set of characteristics ofthe object with an application of one or more of: (1) a temperaturemeasurement of the object; (2) a weight measurement of the object; (3) adetermination of a location of the object on the screen; (4) an imagecapture of the object; (5) determining a type of the object with an aidof a set of applications which set includes one or more applicationsbased on an object recognition technology; (6) a determination of a setof physical dimensions of the object; (7) a determination of a physicalstate of the object; (8) a determination of a mobility of the object;(9) a determination of a viscosity of the object; and track one or moreof a set of dynamic characteristics of the object with an update ofvalues from one or more of said procedures.
 4. The device of claim 1,wherein: said utility configuring the device to includes configuring thedevice to simultaneously detect multiple objects at one or more areas ofthe touch screen with the aid of a multi-detection mechanism; and saidutility configuring the device to determine includes configuring thedevice to determine the set of characteristics of the multiple objects.5. A computer program product comprising: a computer readable storagedevice; and program code on said computer readable storage device thatwhen executed by a processing device having a touch screen display(touch screen), provides the functions of: receiving data indicating adetection of an occurrence of a contact by one or more objects with thetouch screen; automatically determining a set of characteristics of theone or more objects following the occurrence of the contact with thetouch screen; and dynamically activating a set of maintenance actions toenhance a level of cleanliness of the touch screen; displaying a list ofmaintenance tasks to be completed by a user to execute a maintenanceaction; enabling execution of the maintenance action via the displayedlist, wherein a user is able to interact with said list to indicate acompletion of one or more tasks on the list providing a maintenanceaction via an external screen protection device, wherein said screenprotection device has a blue-tooth capability, which enablescommunication between the protection device and the electronic device inorder to provide an appropriate set of details of the affected area ofthe screen to the protection device; detecting one or more defects inone or more display screen pixels; and when a defect is detected,triggering a set of maintenance actions based on a defect of the displayscreen pixels; wherein a discovery of said defect of the screen pixelsis facilitated by one or more maintenance actions which include acleaning action of the touch screen, wherein said maintenance actionsenable an identification of a persistent problem with the screendisplay, which is not attributable to the level of cleanliness of thescreen; and wherein said defect of the screen pixels is confirmed by aset of results obtained by a test of the screen pixels.
 6. The computerprogram product of claim 5, wherein for at least one object of the oneor more objects, said program code further comprises code for:identifying the set of characteristics of the object with an applicationof one or more of the following procedures: (1) a temperaturemeasurement of the object; (2) a weight measurement of the object; (3) adetermination of a location of the object on the screen; (4) an imagecapture of the object; (5) determining a type of the object with an aidof a set of applications which set includes one or more applicationsbased on an object recognition technology; (6) a determination of a setof physical dimensions of the object; (7) a determination of a physicalstate of the object; (8) a determination of a mobility of the object;(9) a determination of a viscosity of the object; tracking one or moreof a set of dynamic characteristics of the object with an update ofvalues from one or more of said procedures; storing data pertaining tothe set of characteristics of the object; and performing a number ofmaintenance checks at a set of specific time intervals based on one ormore of the following: (1) a set of configuration data; and (2) a set ofdata stored in one or more files of maintenance records and results. 7.The computer program product of claim 5, wherein said code foractivating further comprises code for: triggering the set of maintenanceactions as a result of one or more of the following factors: (1) acharacteristic of a detected object; (2) a threshold level attainedfollowing the occurrence of the contact, wherein said threshold is basedon one or more factors contained within a maintenance configurationfile; (3) an elapsed time interval since a last maintenance action; (4)an identified level of screen cleanliness that is determined by one ormore procedures, including utilization of opacity sensors; (5) a time ofday; (6) a level of interaction between a user and the touch screen; and(7) a set of configuration data.
 8. The computer program product ofclaim 7, further comprising code for: applying the set of maintenanceactions, including one or more of the following: (1) a visual change ina particular screen location; (2) an audio alert; (3) a usagerestriction of the screen area; (4) a temperature alert; (5) amodification of a pixel resolution around the particular area; and (6) aconstant indicator, wherein said constant indicator includes one or moreof and is not limited to the following: (a) a visual effect thatincludes a highlighting mechanism facilitated by a display of one ormore of icons and arrows on the screen at a location within a presetrange of distances to the affected area; (b) a touch sensory mechanismthat includes one or more of a heating and cooling of an affected screenarea when touched by the object; and (c) an audio sensory mechanism thatincludes a sound that increases in sound level when an object ispositioned within a defined proximity of the affected area; (7) anapplication of a transparent film to the screen surface; and (8) autilization of a wiper mechanism that dispenses cleaning material acrossthe screen surface.